Skip to content

Conversation

etpinard
Copy link
Contributor

... as v1.1.0 is only compatible with karma-jasmine@2x - making npm run test-jasmine work again.

Cherry-picked from #3868

... as v1.1.0 is only compatible with karma-jasmine@2x
@etpinard
Copy link
Contributor Author

A fixup from #3867

@etpinard
Copy link
Contributor Author

etpinard commented May 20, 2019

Oh boy. Turns out our jasmine tests haven't been running at all on CI ever since #3867 got merged 😡

They have been "failing" as:

image

silently (i.e. w/o an error code 1). So CI wasn't able to catch a failing test from #3869 properly. Commit 8e346b3 fixes that.

Now test-jasmine should really exit with code 1 in cases like this one. karma-jasmine@v2 seems to behave like that. So maybe we should look into spending time on #3368 in the near future.

@archmoj
Copy link
Contributor

archmoj commented May 20, 2019

💃

@etpinard etpinard merged commit 863e8d0 into master May 20, 2019
@etpinard etpinard deleted the fix-jasmine-tests branch May 20, 2019 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants